NTISthis.com

Evidence Guide: ICTPRG410 - Build a user interface

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG410 - Build a user interface

What evidence can you provide to prove your understanding of each of the following citeria?

Build a prototype user interface (UI)

  1. Gather the requirements for the UI
  2. Determine the application development language for writing the UI
  3. Build a prototype, using the prototyping tools available in the determined language
  4. Review the UI prototype with the client, and edit as required
Gather the requirements for the UI

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the application development language for writing the UI

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Build a prototype, using the prototyping tools available in the determined language

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the UI prototype with the client, and edit as required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design the UI

  1. Formulate the application content flow
  2. Design the UI components
  3. Define UI actions
  4. Itemise UI events
Formulate the application content flow

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design the UI components

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define UI actions

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Itemise UI events

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Build the UI

  1. Determine the appropriate language
  2. Build the UI with the required functionality
Determine the appropriate language

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Build the UI with the required functionality

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test the UI

  1. Test the UI for overall functionality, according to requirements
  2. Iterate the UI design, or build, until the test results meet requirements
Test the UI for overall functionality, according to requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Iterate the UI design, or build, until the test results meet requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the UI and obtain client sign-off

  1. Document the user requirements
  2. Document the UI
  3. Obtain client sign-off to the completed UI
Document the user requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the UI

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Obtain client sign-off to the completed UI

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Build a prototype user interface (UI)

1.1 Gather the requirements for the UI

1.2 Determine the application development language for writing the UI

1.3 Build a prototype, using the prototyping tools available in the determined language

1.4 Review the UI prototype with the client, and edit as required

2. Design the UI

2.1 Formulate the application content flow

2.2 Design the UI components

2.3 Define UI actions

2.4 Itemise UI events

3. Build the UI

3.1 Determine the appropriate language

3.2 Build the UI with the required functionality

4. Test the UI

4.1 Test the UI for overall functionality, according to requirements

4.2 Iterate the UI design, or build, until the test results meet requirements

5. Document the UI and obtain client sign-off

5.1 Document the user requirements

5.2 Document the UI

5.3 Obtain client sign-off to the completed UI

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Build a prototype user interface (UI)

1.1 Gather the requirements for the UI

1.2 Determine the application development language for writing the UI

1.3 Build a prototype, using the prototyping tools available in the determined language

1.4 Review the UI prototype with the client, and edit as required

2. Design the UI

2.1 Formulate the application content flow

2.2 Design the UI components

2.3 Define UI actions

2.4 Itemise UI events

3. Build the UI

3.1 Determine the appropriate language

3.2 Build the UI with the required functionality

4. Test the UI

4.1 Test the UI for overall functionality, according to requirements

4.2 Iterate the UI design, or build, until the test results meet requirements

5. Document the UI and obtain client sign-off

5.1 Document the user requirements

5.2 Document the UI

5.3 Obtain client sign-off to the completed UI

Evidence of the ability to:

design a fully functional user interface (UI) in consultation with the user, using the determined language

create a prototype UI

review the prototype with the user

build the UI

test that the UI is complete, consistent and functional

document the user requirements, UI and client sign-off.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

apply a range of basic mathematical strategies

use object-oriented programming

use open-source development tools

describe the process of small-size application development.